feat: restructure repository by akihikokuroda · Pull Request #40 · generative-computing/mellea-contribs

akihikokuroda · 2026-03-18T19:01:39Z

fix #38

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

mergify · 2026-03-18T19:02:15Z

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟢 Enforce conventional commit

Wonderful, this rule succeeded.

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

title ~= ^(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert|release)(?:\(.+\))?:

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

Add detect-changes job that checks which subpackages have been modified and outputs flags for each. Each subpackage workflow now only runs when: - Its files in mellea_contribs/ are changed, OR - Its corresponding quality workflow file is changed This prevents unnecessary CI runs when only unrelated subpackages are modified. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

jakelorocco

Is it possible to make the workflows dynamic? Ie instead of having to create a new one for each subpackage, we just mandate all folders under mellea_contribs are subpackages and require some sort of structure?

Even if we don't have that, we should make sure to have a version of the quality check that ensures new packages have tests. For example, if I make a new subpackage and don't add tests / quality workflows right now, will I be able to merge? Or there's some necessary check still?

I'm also not certain how these differently named checks interact with github branch protections? For the mellea repo, we have to specifically select checks.

akihikokuroda · 2026-03-20T16:34:19Z

@jakelorocco A new CI that checks if each subpackage has its own ci can be added. The quality of each ci is up-to the subpackage though. Is it enough as a minimum?

jakelorocco · 2026-03-20T17:09:09Z

@jakelorocco A new CI that checks if each subpackage has its own ci can be added. The quality of each ci is up-to the subpackage though. Is it enough as a minimum?

I think that makes sense. We should vet CI at merge time, but a check will ensure nothing gets through accidentally.

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

psschwei · 2026-03-23T13:17:10Z

Once this merges, we'll also need to update the required checks in the branch protections ( as the quality checks no longer exist)

psschwei · 2026-03-23T13:20:25Z

.github/workflows/ci.yml

 on:
-  pull_request:
-    types: [opened, reopened, synchronize]
+  workflow_dispatch:


this would need to be run manually right? would this be more for auditing or do you see another purpose?

Yes, this must be run manually. I just left it for convenience. It can be deleted.

So we can't have checks on this repo then? Or the checks just need to be manually kicked off for a given branch / PR?

I also don't know how branch protections interact with this. And also, if this is the case, why are the github action runners showing that checks ran below in the PR?

psschwei · 2026-03-23T13:25:27Z

.github/workflows/ci-crewai-backend.yml

+  push:
+    branches:
+      - main
+    paths:


since all the backends depend on mellea-integration-core, there is the chance that if we change something in the core that it would break the backends... should we also trigger a run of the backends if the core changes?

That's right. I'll add mellea-integration-core change in all integration paths.

I don't think we should create cross-dependencies in this repo. See my comment below, but if we update mellea-integration-core and it forces us to update other packages, then we've just inherited a ton of maintenance work.

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

psschwei · 2026-03-23T15:41:17Z

mellea_contribs/mellea-integration-core/pyproject.toml


 dependencies = [
-    "mellea>=0.3.2",
+    "mellea==0.3.2",


do we want to bump this to 0.4.0?
longer-term, we probably need to sync our update strategy here to the release process
cc @jakelorocco

I only flagged one, but there are multiple places we may need to update if we do want to bump

Some tests failed with 0.4.0. Bumping 0.4.0 will be follow up PR.

I think it's fine for these to lag behind mellea (and expected since we don't want to own all the maintenance here). What happens if we bump mellea-integration-core? Do the internal packages that rely on it in here also have to get bumped? If so, that seems untenable.

psschwei

I think I am largely good with the changes here. would be good to have a review from the core team as well

jakelorocco

I think this is looking good and on the right track. The main purpose of my comments is to make longterm support from the Mellea team much less burdensome in this repo. To me, that means automating a large amount of the testing process and ensuring subpackages can be updated independently when needed.

jakelorocco · 2026-03-24T13:08:43Z

run_tests.sh

+# Test reqlib_package (may have dependency issues)
+echo "=========================================="
+echo "Testing: reqlib_package"
+echo "=========================================="
+echo -e "${YELLOW}Note: reqlib_package requires additional dependencies (citeurl, eyecite, playwright)${NC}"
+cd "$REPO_ROOT/mellea_contribs/reqlib_package"
+if PYTHONPATH="src:$PYTHONPATH" python3 -m pytest test/ -v --tb=short 2>&1; then
+    echo -e "${GREEN}✓ reqlib_package tests PASSED${NC}"
+    PASSED_PROJECTS+=("reqlib_package")
+else
+    echo -e "${YELLOW}⚠ reqlib_package tests SKIPPED (missing dependencies)${NC}"
+    FAILED_PROJECTS+=("reqlib_package (missing deps)")
+fi
+echo ""
+
+# Test tools_package (may have dependency issues)
+echo "=========================================="
+echo "Testing: tools_package"
+echo "=========================================="
+echo -e "${YELLOW}Note: test_mprogram_robustness.py requires 'benchdrift' package (skipped)${NC}"
+cd "$REPO_ROOT/mellea_contribs/tools_package"
+if PYTHONPATH="src:$PYTHONPATH" python3 -m pytest test/test_double_round_robin.py test/test_top_k.py -v --tb=short 2>&1; then
+    echo -e "${GREEN}✓ tools_package tests PASSED (2 tests, test_mprogram_robustness.py skipped - requires benchdrift)${NC}"
+    PASSED_PROJECTS+=("tools_package")
+else
+    echo -e "${YELLOW}⚠ tools_package tests FAILED${NC}"
+    FAILED_PROJECTS+=("tools_package")
+fi
+echo ""


We should mandate that all projects have the same structure. We shouldn't need to specify different commands here than from the run_project_tests above.

jakelorocco · 2026-03-24T13:10:29Z

mellea_contribs/mellea-integration-core/pyproject.toml


 dependencies = [
-    "mellea>=0.3.2",
+    "mellea==0.3.2",


I think it's fine for these to lag behind mellea (and expected since we don't want to own all the maintenance here). What happens if we bump mellea-integration-core? Do the internal packages that rely on it in here also have to get bumped? If so, that seems untenable.

jakelorocco · 2026-03-24T13:11:30Z

.github/workflows/ci-crewai-backend.yml

+  push:
+    branches:
+      - main
+    paths:


I don't think we should create cross-dependencies in this repo. See my comment below, but if we update mellea-integration-core and it forces us to update other packages, then we've just inherited a ton of maintenance work.

jakelorocco · 2026-03-24T13:12:16Z

mellea_contribs/tools_package/README.md

@@ -0,0 +1 @@
+README.md


I think we should either remove the README.md or add something here (even if it's auto generated). There's another README.md with the same problem.

jakelorocco · 2026-03-24T13:13:07Z

.github/workflows/ci.yml

I might have missed it, but does this introduce the auto-detect packages without testing that we talked about?

jakelorocco · 2026-03-24T13:14:13Z

.github/workflows/ci.yml

+  detect-changes:
+    runs-on: ubuntu-latest
+    outputs:
+      mellea-integration-core: ${{ steps.changes.outputs.mellea-integration-core }}
+      crewai-backend: ${{ steps.changes.outputs.crewai-backend }}
+      dspy-backend: ${{ steps.changes.outputs.dspy-backend }}
+      langchain-backend: ${{ steps.changes.outputs.langchain-backend }}
+      reqlib-package: ${{ steps.changes.outputs.reqlib-package }}
+      tools-package: ${{ steps.changes.outputs.tools-package }}


I feel like instead of having to manually add a bunch of boilerplate for any new package that gets added to this repo, we should enforce a required package structure. Then, we don't need to duplicate this code and can just auto-process any new additions and automatically handle new packages in CI runs.

jakelorocco · 2026-03-24T13:14:51Z

.github/workflows/ci.yml

 on:
-  pull_request:
-    types: [opened, reopened, synchronize]
+  workflow_dispatch:


So we can't have checks on this repo then? Or the checks just need to be manually kicked off for a given branch / PR?

akihikokuroda · 2026-03-24T13:29:29Z

@jakelorocco I'm taking out ci.yml, README.md and run_test.sh. They are not necessary and may be causing issues later. I also take back the changes mellea_integration_core kicking the 3 integrations ci.

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

akihikokuroda · 2026-03-24T13:59:19Z

:-(

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

akihikokuroda added 7 commits March 18, 2026 09:26

move integrations under mellea_contribs

e25e44e

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

move reqlib and tools src

250c646

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

separate and move tests and docs

610a819

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

duplucate pyproject.toml and uv.lock to tools amd reqlib packages

73328e1

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

duplucate pyproject.toml and uv.lock to tools amd reqlib packages

f748111

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

adjust imports and fix tests

423bc9b

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

update ci and fix some file path

f61fe4b

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

akihikokuroda marked this pull request as draft March 18, 2026 19:01

akihikokuroda mentioned this pull request Mar 18, 2026

feat: multi packages #37

Closed

akihikokuroda added 20 commits March 18, 2026 15:29

fix ci yaml error

bb428c1

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

fix ci yaml error

5734cd1

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

fix ci yaml error

b0266d4

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

fix ci yaml error

f52e68b

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

pin mellea (0.3.2) and fix CI of mellea-integration-core

fc9f9fc

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

fix venv issue

39edddf

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

fix venv issue

6a14bb7

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

fix venv issue

15c178c

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

fix venv issue

3528977

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

add langchain ci

73bddfe

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

add the rest of packages

c973014

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

add the rest of packages

ff5d71c

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

debug

8d98f4e

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

python version requirement change

313bd74

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

disable integration test in dspy

233837a

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

test reqlib ci

eee34af

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

test reqlib ci

6220636

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

test tools ci

5a02668

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

add empty READMEs

8e4b043

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

fixing tools reqlib

fbfcaae

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

akihikokuroda and others added 5 commits March 19, 2026 14:08

fixing tools reqlib

d785039

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

fixing tools reqlib

9b4736d

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

avoid conflict

5db88a5

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

separate ci

d71bfd3

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

akihikokuroda marked this pull request as ready for review March 19, 2026 20:38

akihikokuroda requested review from a team, avinash2692, jakelorocco and psschwei March 19, 2026 20:42

jakelorocco reviewed Mar 20, 2026

View reviewed changes

add ci checking ci coverage

88896ab

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

psschwei reviewed Mar 23, 2026

View reviewed changes

review comments

e48cbe8

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

psschwei reviewed Mar 23, 2026

View reviewed changes

jakelorocco reviewed Mar 24, 2026

View reviewed changes

review comments

2426612

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

akihikokuroda added 2 commits March 25, 2026 16:04

disable unstable test

beefd40

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

add empty README.md

0d40973

Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>

akihikokuroda requested review from jakelorocco and psschwei March 25, 2026 22:07

Conversation

akihikokuroda commented Mar 18, 2026

Uh oh!

mergify bot commented Mar 18, 2026

Merge Protections

🟢 Enforce conventional commit

Uh oh!

jakelorocco left a comment

Choose a reason for hiding this comment

Uh oh!

akihikokuroda commented Mar 20, 2026

Uh oh!

jakelorocco commented Mar 20, 2026

Uh oh!

psschwei commented Mar 23, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

psschwei left a comment

Choose a reason for hiding this comment

Uh oh!

jakelorocco left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

akihikokuroda commented Mar 24, 2026

Uh oh!

akihikokuroda commented Mar 24, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants